Branch names

You are here: About configuring Meridian > Branch names

Branch names

Vault branches
Setting	Branch	Description
BRANCH_ARCHIVE	Archive	Stores retired documents or older revisions created with the Create New Version or Create Project Copy commands. This branch is mandatory in almost all scenarios.
BRANCH_CONTROLLED	Masters	Stores released documents of the Plant Document document type. This branch is mandatory when that type is used.
BRANCH_UNCONTROLLED	Project	Stores unreleased documents of the Plant Document document type. This branch is mandatory when that type is used.
BRANCH_OBJECTS	Objects	Stores unreleased documents of the Object document type. This branch is mandatory when that document type is used.
BRANCH_GENERIC	Miscellaneous	Stores unreleased document of the Generic Document document type. This branch is mandatory when that type is used.
BRANCH_RENDERED	Renditions	Stores unreleased document of the Generic Document document type. This branch is mandatory when the BlueCielo Publisher is used. The Publisher does not look for this branch and no modifications to the Publisher setup are required when changing this branch name.

Vault branches

Setting

Branch

Description

BRANCH_ARCHIVE

Archive

Stores retired documents or older revisions created with the Create New Version or Create Project Copy commands. This branch is mandatory in almost all scenarios.

BRANCH_CONTROLLED

Masters

Stores released documents of the Plant Document document type. This branch is mandatory when that type is used.

BRANCH_UNCONTROLLED

Project

Stores unreleased documents of the Plant Document document type. This branch is mandatory when that type is used.

BRANCH_OBJECTS

Objects

Stores unreleased documents of the Object document type. This branch is mandatory when that document type is used.

BRANCH_GENERIC

Miscellaneous

Stores unreleased document of the Generic Document document type. This branch is mandatory when that type is used.

BRANCH_RENDERED

Renditions

Stores unreleased document of the Generic Document document type. This branch is mandatory when the BlueCielo Publisher is used. The Publisher does not look for this branch and no modifications to the Publisher setup are required when changing this branch name.

All branch names must be unique. Most branches can be renamed with little consequences. However the following points should be taken into account.

Branches can only be renamed when they contain no locked documents. Only the Miscellaneous, Masters, and Projects branches can contain locked documents.

The Projects branch has two sub-branches to separate Design and As-Built projects. The branch names are determined with the following settings.

Projects branch names
Setting	Branch
PROJECT_BRANCH_ASBUILT	As-Built
PROJECT_BRANCH_DESIGN	Design

Projects branch names

Setting

Branch

PROJECT_BRANCH_ASBUILT

As-Built

PROJECT_BRANCH_DESIGN

Design

The As-Built and the sub-project project type names are defined the following settings. All other project types that can be created are considered a Design project.

Non-Design project types
Setting	Project Type
PROJECT_ASBUILTPROJECT	As-Built
PROJECT_SUBPROJECTTYPE	ContractorJob

Non-Design project types

Setting

Project Type

PROJECT_ASBUILTPROJECT

As-Built

PROJECT_SUBPROJECTTYPE

ContractorJob

Because branch names should not be used in filter conditions because they can easily be changed, use properties like StatusPublished, Rendition, and RetentionModifiedBy and document type filters instead to filter out functionality.

Related concepts

Navigation views

Project naming convention

Scopes


	BlueCielo Meridian REFSYS 2012 Configuration Guide \| BlueCielo ECM Solutions